Chama Meeting 01_04_2023

January 4, 2023

Jacob Specht

1.0

Chama Meeting 1/4/2023

Started talking about the input file and SWMM in general.

Initial loading is 40 Ci/acre, more than the defined 0.44 Ci/acre. Idea is with a highly contaminated area, how long would it take to no longer be contaminated. The lower one is the trigger level, we want to trigger at that level or higher. Loading values in the inp file are correct, based on contamination from a dirty bomb.
Katherine's version of PySWMM has the surface level concentration (is this the right variable name?) available. Concentration is available at any time as opposed to only at the end. She's out of the office this week, but a conversation would be helpful.
API documentation possibly hasn't been updated. Info about the subcatch load (is this the right variable name?) isn't available. That specific page in docs was updated 2/21/2017, so probably needs to be re-built. https://pyswmm.readthedocs.io/en/latest/reference/toolkitapi.html https://github.com/OpenWaterAnalytics/pyswmm/blob/master/docs/source/reference/toolkitapi.rst
25 locations not 25 sensors. We haven't tried more than 6 locations at a time.
GUI provides output on timestep whereas pyswmm is on every x iter. Outputs aren't initially comparable until we grab numbers from reporting timestep.
Changed from Curies to Picocuries. Washoff report will still be in log values. Zero values are actually zero, not log.

General switch in conversation from SWMM to Chama.

2 scenarios, plume1 and plume2.
Do each scenario individually first. Time permitting, we can do both at the same time later.
More interested in impact, less in coverage.
Particle tracing through subcatchments, probably beyond scope.
Anne will check their library for a paper that might be useful (Melissa will be emailing her the paper info).
Should we add Anne to the github repo, or just give her deliverables at the end of it?
They were talking about GitHub pages instead of readthedocs. Also compiling into PDF for a more static user manual type resource.

Closing Conversation

Example 6 is fine for debugging runtime errors (not data validity) but in general we should only be running Banklick.

SWMOPT Meeting 01042023.docx